< previous page page_235 next page >

Page 235
learned about assessing terminology and traceability, including domain-specific terminology for the Samsona Bank Teller example, and related traceability issues involved in refining use cases. Tomorrow, you'll learn the fundamental concepts necessary to implement a Graphical User Interface Subsystem. The lesson for Day 12, Graphical User Interface Subsystems: An Example, continues the presentation of the GUI subsystem, giving you actual implementation advice and code.
Q&A
Q True or False: The most experienced developers who don't use object technology have done some form of iterative development.
A True
Q What should you do when you make a discovery about the domain while in the middle of any project phase?
A If the discovery is important enough, you must resolve it with analysis and design activities before implementing the new requirement.
Q What is an iteration plan?
A An iteration plan captures the project activities you and your team members must perform, as well as delivery of the artifacts that result from these activities.
Q What is a negative side effect of prematurely creating a static iteration plan?
A Creating a static iteration plan prematurely often (but not necessarily) results in frustration and low morale.
Q How important are use cases?
A The use-case model is the backbone of a project. All the artifacts in the object-oriented project are dependent on it in one way or another.
Q Briefly, what is reverse engineering and forward engineering?
A Modeling existing user processes is reverse engineering. Modeling the desired model is forward engineering.
Q What can you do if you're overwhelmed with business process discoveries?
A It's best to seek the help of one or more business analysts or business process designers.
Q What is a factor that helps to increase the chances of success for your project?
A Actively including user input to validate your discoveries.
Q What is a red flag that indicates the application architecture is lacking?
A When your project tends to have no interface classes.

 
< previous page page_235 next page >

If you like this book, buy it!